This sample shows how to access the ATI RAVE context from a QD3D app. This allows the app developer to set most RAVE state variables from a QD3D app. The demo displays a spinning cube with a texture mapped on to its sides. Clicking the mouse will stop the spinning and also toggle the RAVE texture filtering state. The current filtering state and frame rate are displayed at the top of the window. The texture, "sun.PICT" is a copy of the scrapbook sun image, scaled down to 64x64 to show the benefits of texture filtering.
Previously, in QD3D it was not possible to find out the current RAVE context pointer. The method shown here, should be entirely safe. This technique will only set RAVE state if an ATI RAVE context is current on the specified hardware device. Thus if a given device has no ATI hardware or drivers installed, then the method is a no-op. Currently this demo only attempts to set RAVE state for windows that are entirely on an ATI RAVE card. To handle windows partially overlapping an ATI device would require potentially setting RAVE state on multiple contexts.
This sample also demonstrates how to register for a RAVE callback from QD3D. This means that at the end of each frame RAVE will callback to a user-supplied function and let the application modify the contents of the back buffer just before this buffer is copied to the screen. This can be used for getting access to the back buffer for printing or other image processing tasks. A QD3D app can also register for other RAVE callbacks.
